home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_1
/
evd41.zip
/
EVD_UTIL.ZIP
/
EVD_UTIL.DOC
< prev
next >
Wrap
Text File
|
1992-03-01
|
5KB
|
123 lines
EVDoor 4.0 Utilities
PCBSTATS.EXE (By: CDC - Developers of PCBoard)
This is the "latest" version of CDC's PCBSTATS program. This
program updates your call awaiting screens. You *must* have this
program (PCBSTATS.EXE) in the same directory as your PCBOARD.SYS
is located (ALL NODES if your a multi-node user). And you *must*
have your PCBSTATS.DAT in the same location as your USERS files.
EVDoor uses PCBSTATS.EXE to update your call awaiting screens when
a user disconnects or is automatically disconnected.
EVDPURGE.EXE (By: Eagleware - The Eagle's Nest)
This utility will compare your USERS file against EVDoor's
VERIFY.FON file. If the program finds a "MATCH" on a "USER NAME"
when reading your USERS file and then finds the same "USER NAME" in
the VERIFY.FON file, it will write that entry out to disk. In other
words, it comparers your current USERS against the USERS listed in
VERIFY.FON, and basically DELETES those entries in the VERIFY.FON
file that are NOT current USERS on your system. EVDPURGE first
makes a backup copy your current VERIFY.FON file to the filename
VERIFY.FBK. Then creates a filename of VERIFY.TMP, all "USER NAME"
matches are written to this file. When the process is complete, it
renames VERIFY.TMP to VERIFY.FON. The process of reading in each
"USER NAME" and running a line by line check of VERIFY.FON is very
SLOW! So, you probably want to run this in your PCBoard event. Make
absolutely sure that no other program is accessing the VERIFY.FON
file or USERS file when you run EVDPURGE. You must run EVDPURGE
from the EVDoor directory!
USAGE
EVDPURGE C:\PCB\MAIN\USERS
^
A
A = Path & filename to your USERS file
DELAY.EXE (By: EagleWare - The Eagle's Nest)
This program will delay/pause from 0 to 10 seconds. You should run
this program if you are running multi-nodes and will be using
EVDoor on several nodes. This will allow a delay in opening the
door, so that a conflict will not occurred if several users try
accessing the door at the same time.
USAGE
DELAY 5
^
A
A = Number of seconds to delay/wait (0-10);
PROECHO.COM (By: Sam Smith - The Tool Shop BBS)
This is a utility to display a single line message to the user when
opening EVDoor. Use this in conjunction with DELAY.EXE
USAGE
PROECHO 1 ~ Please wait, checking Network Status...~
^ ^ ^ ^
A B C D
A = COM PORT to display message to (1 or 2),
B = Send a line feed (~).
C = Message to display.
D = Send another line feed (~).
FATAL142.ZIP (By: Sam Smith - The Tool Shop BBS)
Use this (TSR) program if you will be running multi-nodes. This
excellent program will help alleviate a "FATAL file Sharing
violation". For example, should a user be using EVDoor and writing
to the callers log, and you are on another node and want to view
the callers log this would create a file sharing violation within
EVDoor and would stay there until you manually retry or reboot your
system/node running EVDoor. This is only a temporary fix, until I
can properly set file sharing up on the callers log file. Place
FATAL/I in your autoexec.bat or you can put it in your
startnet.bat. The benefits of using this program out weight the
very little memory it uses as a TSR.
USAGE
FATAL/I
^
A
A = Install
TXT2MB220.ZIP (By: Robert Vostrey - The Faster than Light BBS)
EVDoor will return an ERRORLEVEL of 60 when a user has been
successfully verified. You can use this ERRORLEVEL to redirect a
batch file, and use TXT2MSG.EXE to place a pre-written "welcome"
message to your newly verified users in your message base. TXT2MSG
uses PCBOARD.SYS file to find information about the user, when
EVDoor automatically disconnects the user, it basically wipes out
the needed information from within PCBOARD.SYS, so you will need to
use PCBCOPY.EXE to make a "copy" of the PCBOARD.SYS file before
running EVDoor, you can do this within the EVDoor batch file, and
then use the copy of PCBOARD.SYS for TXT2MSG.EXE to use.
USAGE
See manual within TXT2MB220.ZIP and TXT2MSG batch file.
OUTCOMM.ZIP (By: Cam DeBuck)
This can be used in leu of PROECHO, as it suppose to support
non-standard comm ports. The difference between PROECHO and OUTCOMM
is that PROECHO takes information to be displayed on the command
line used to call up PROECHO, whereas OUTCOMM will display a
pre-written ASCII text file.
USAGE
See manual within OUTCOMM.ZIP
INSTAREG
Sample batch file to use with EVDoor and InstaReg.
TXT2MSG
Sample batch file to use with EVDoor and TXT2MB220.ZIP